All system start-up files must be owned by root.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-4089	GEN001660	SV-38420r1_rule	ECLP-1	Medium

Description
System start-up files not owned by root could lead to system compromise by allowing malicious users or applications to modify them for unauthorized purposes. This could lead to system and network compromise.

STIG	Date
HP-UX 11.31 Security Technical Implementation Guide	2017-12-08

Details

Check Text ( C-36372r2_chk )
System start-up files are identified as follows: Run control scripts reside in the /sbin/init.d directory. Links to the run control scripts exist in the /sbin/rc.d directories. Run control configuration files exist in the /etc/rc.config.d directory. Check all system start-up script file ownership. # ls -lL /sbin/init.d/ /sbin/rc.d/ /etc/rc.config.d/* If any system start-up script file is not owned by root or bin, this is a finding.

Check Text ( C-36372r2_chk )

System start-up files are identified as follows:

Run control scripts reside in the /sbin/init.d directory.

Links to the run control scripts exist in the /sbin/rc*.d directories.

Run control configuration files exist in the /etc/rc.config.d directory.

Check all system start-up script file ownership.
# ls -lL /sbin/init.d/* /sbin/rc*.d/* /etc/rc.config.d/*

If any system start-up script file is not owned by root or bin, this is a finding.

Fix Text (F-31709r1_fix)
Change the ownership of the run control script(s) with incorrect ownership. # chown root